5.3.3 APPX Application Design Manual

+ Chapter 1-1: Overview of Application Design
+ Chapter 1-2: Getting Started
+ Chapter 1-3: Data Dictionary
+ Chapter 1-4: Understanding Process Design
+ Chapter 1-5: Interprocess Communication
+ Chapter 1-6: Customizing Your Application
+ Chapter 1-7: The Documentation Facility
+ Chapter 1-8: Application Design Tools
+ Chapter 2-1: Data Dictionary Overview
+ Chapter 2-2: Data Dictionary Concepts
+ Chapter 2-3: Domains
+ Chapter 2-4: Files and Fields
+ Chapter 2-5: Work Fields
+ Chapter 3-1: Overview of APPX Processes
+ Chapter 3-2: Getting Started
+ Chapter 3-3: Process Definition
+ Chapter 3-4: Menu Processes
+ Chapter 3-5: Job Processes
+ Chapter 3-6: Input Processes
+ Chapter 3-7: Output Processes
+ Chapter 3-8: Update Processes
+ Chapter 3-9: Query Processes
+ Chapter 3-10: Inquiry Processes
+ Chapter 3-11: Status Processes
+ Chapter 3-12: Subroutine Processes
+ Chapter 3-13: Table Processes
- Chapter 3-14: Automatic and Optional Children
+ Chapter 3-15: Using the Image Editor
+ Chapter 3-16: Using GUI Features of the Image Editor
+ Chapter 3-17: Using Event Points
+ Chapter 4-1: ILF Integration
+ Chapter 4-2: True/False Status Indicators
+ Chapter 4-3: Specifying Statements
+ Chapter 4-4: The ILF Editor
+ Chapter 4-5: The Appx ILF Debugger
+ Chapter 4-6: ILF Keyword Reference
+ Chapter 4-7: Predefined Fields
+ Chapter 4-8: Runtime Subroutine's and Predefined Processes
+ Chapter 4-9: Appx Chart Director API

Chapter 3-14: Automatic and Optional Children

Child Use Query Option


For automatic child processes, the Use Query option identifies a specific query process by Application and Process Name that determines the records available to this child process. This specification affects input, output, and update processes. The Query Name on the Use Query option screen will default to the prior query entered in the job stream.  If the name of the query is changed you must change this entry on the Use Query specification to match if that is your intention.  The child Use Query overlay is shown below.

Child Use Query Overlay

The child Use Query overlay contains the following fields.

Query Name. The PCF of the query that is identified by this specification must match the PCF of the child process.

Update Type determines the disposition of any existing pointer file for the query process to be used. The query Update Type options are:

1 - NORMAL. Generate the pointer file if it does not yet exist. If the pointer file exists, use it without re-executing the query.

2 - CLEAR. Discard any existing pointer file and generate a new one.

3 - CASCADE. Apply any new constraints to further restrict the contents of an existing pointer file.

Note that if the new constraints are less restrictive than the constraints that were used to generate the existing pointer file, the CASCADE option will not add records to the pointer file. In such a case, you should use the CLEAR option.

Also, if you intend to reuse an existing pointer file and yet repeat the query setup, be sure that you specify CHANGE as the Override Default Mode in the Additional Attributes for the second query.

The default is 2 (CLEAR).

Application Design Manual                                         "Powered by Appx Software"

1125

©2006 By APPX Software, Inc. All Rights Reserved